Lossless socket-based layer 4 transport (reliability) system for a converged ethernet network

ABSTRACT

A reliability system for a Converged Enhanced Ethernet network may include a plurality of end points each comprising a layer 4 transport layer, where each end point is connected to a data center bridging (DCB) layer 2 network. The system may also include an adaptor between the layer 4 transport layer and the DCB layer 2 network to translate at least one of flow and congestion control feedback signals, provided by at least one of the DCB network and the transport layer, to consolidated feedback signals for controlling transmission by the transport layer.

BACKGROUND

The invention relates to the field of computer networking, and, moreparticularly, to Ethernet networks.

Converged Enhanced Ethernet (CEE) datacenters allow high link speeds andshort delays while introducing lossless operation (and lossless trafficclasses) by the means of link layer flow control (LL-FC, a.k.a. PriorityFlow Control (PFC) in CEE) beyond the traditional lossy operation (lossytraffic classes). However, in contrast to the traditional Ethernet andInternet, the lossless operation of CEE introduces new challenges.

SUMMARY

According to one embodiment of the invention, a reliability system for aConverged Enhanced Ethernet network may include a plurality of endpoints each comprising a layer 4 transport layer, where each end pointis connected to a data center bridging (DCB) layer 2 network. The systemmay also include an adaptor between the layer 4 transport layercomprising one or more protocols, such as TCP, UDP, RCP, DCCP, XCP,etc., and the DCB layer 2 network to translate at least one of flow andcongestion control feedback signals, provided by at least one of the DCBnetwork and the transport layer, to consolidated feedback signals forcontrolling transmission by the transport layer.

The DCB layer 2 network may generate flow control signals according to aflow control protocol supporting multiple priorities, such as PriorityFlow Control (PFC). The DCB layer 2 network may generate congestioncontrol feedback signals according to a quantized congestionnotification (QCN) protocol. PFC and QCN can be individually orsimultaneously enabled in the DCB layer 2 network. If both PFC and QCNare enabled, either one or both may be independently used by any endpoint.

The end point may be connected to the DCB layer 2 network through an endstation, wherein the end station implements a quantized congestionnotification (QCN) reaction point imposing rate limits based on a QCNprotocol to limit network congestion in the DCB layer 2 network inresponse to receiving congestion control signals. The network trafficgenerated by the transport layer may be carried on layer 2 with lossyoperation, either by configuring the end station to steer the traffic toa lossy priority of a priority flow control (PFC) protocol, or by notusing any PFC protocol.

The network traffic generated by the transport layer may be carried onlayer 2 with lossless operation, by configuring the end station to steerthe traffic to a lossless priority of a priority flow control (PFC)protocol and by letting the end station react to layer 2 flow controlmessages generated by the adjacent switch. The network traffic generatedby the transport layer may be carried on layer 2 with lossy operation,either by configuring the end station to steer the traffic to a lossypriority of a priority flow control (PFC) protocol, or by not using anyPFC protocol.

The network traffic generated by the transport layer may be carried onlayer 2 with lossless operation, by configuring the end station to steerthe traffic to a lossless priority of a priority flow control (PFC)protocol and by letting the end station react to layer 2 flow controlmessages generated by an adjacent switch.] The adaptor may preprocessthe flow and congestion control feedback signals into consolidatedfeedback signals, with the preprocessing including at least one ofdelaying, aggregating, filtering, replicating, enhancing and decimatingthe primary feedback signals.

The layer 4 transport layer may be a Transmission Control Protocol(TCP), RCP, XCP, DCCP, UDP or any socket-based transport scheme, hereinnamed TCP. The interface may provide a reduced-rate consolidatedfeedback signal indicating congestion severity induced by a TCP flow,and in which the interface comprises a TCP congestion module forcontrolling TCP flow transmissions in response to the consolidatedfeedback signal.

The consolidated feedback signal may comprise at least one of a TCP flowrate limit, a TCP flow buffer occupancy metric, and a TCP flow ratelimit for processing TCP ACKs [if existent, as UDP doesn't employ ACK]or Explicit Congestion Notifications (ECN) and for controllingassociated TCP transmissions. The congestion module adjusts a TCP flowcongestion window and transmission schedule in response to theconsolidated feedback signal.

Another aspect of the invention is a reliability method for a ConvergedEnhanced Ethernet network. The method may include providing a pluralityof end points each comprising a layer 4 transport layer, where each endpoint is connected to a data center bridging (DCB) layer 2 network. Themethod may also include positioning an adaptor between the layer 4transport layer and the DCB layer 2 network to translate at least one offlow and congestion control feedback signals, provided by at least oneof the DCB network and the transport layer, to consolidated feedbacksignals for controlling transmission by the transport layer.

The method may further include generating flow control signals at theDCB layer 2 network according to a flow control protocol supportingmultiple priorities, such as Priority Flow Control (PFC). The method mayadditionally include generating congestion control feedback signals atthe DCB layer 2 network according to a quantized congestion notification(QCN) protocol.

The method may also include connecting the end point to the DCB layer 2network through an end station, where the end station implements aquantized congestion notification (QCN) reaction point imposing ratelimits based on a QCN protocol to limit network congestion in the DCBlayer 2 network in response to receiving congestion control signals. Themethod may further include carrying network traffic generated by thetransport layer on layer 2 with lossy operation, either by configuringthe end station to steer the traffic to a lossy priority of a priorityflow control (PFC) protocol, or by not using any PFC protocol.

The method may additionally include carrying the network trafficgenerated by the transport layer on layer 2 with lossless operation, byconfiguring the end station to steer the traffic to a lossless priorityof a priority flow control (PFC) protocol and by letting the end stationreact to layer 2 flow control messages generated by an adjacent switch.By switch we refer to any physical or virtual device that may be usedfor switching, bridging, steering, sorting, routing, forwarding,scheduling packets or Ethernet frames. The method may also includeprocessing TCP ACKs and/or ECNs, and controlling associated TCPtransmissions where the consolidated feedback signal comprises at leastone of a TCP flow rate limit, a TCP flow buffer occupancy metric, and aTCP flow rate limit. The method may further include adjusting a TCP flowcongestion window and transmission schedule in response to theconsolidated feedback signal via the congestion module.

Another aspect of the invention is a computer readable program codescoupled to tangible media to address reliability in a converged Ethernetnetwork. The computer readable program codes may be configured to causethe program to provide a plurality of end points each comprising a layer4 transport layer, where each end point is connected to a data centerbridging (DCB) layer 2 network. The computer readable program codes mayalso position an adaptor between the layer 4 transport layer and the DCBlayer 2 network to translate at least one of flow and congestion controlfeedback signals, provided by at least one of the DCB network and thetransport layer, to consolidated feedback signals for controllingtransmission by the transport layer.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a Converged Enhanced network inaccordance with the invention.

FIG. 2 is a flowchart illustrating method aspects according to theinvention.

FIG. 3 is a flowchart illustrating method aspects according to themethod of FIG. 2.

FIG. 4 is a flowchart illustrating method aspects according to themethod of FIG. 2.

FIG. 5 is a flowchart illustrating method aspects according to themethod of FIG. 4.

FIG. 6 is a flowchart illustrating method aspects according to themethod of FIG. 4.

FIG. 7 is a flowchart illustrating method aspects according to themethod of FIG. 4.

FIG. 8 is a flowchart illustrating method aspects according to themethod of FIG. 5.

FIG. 9 is a flowchart illustrating method aspects according to themethod of FIG. 5.

FIG. 10 illustrates a prior art hotspot saturation tree in a 5-stage fattree.

FIG. 11 illustrates explicit congestion notification buffering size inthe prior art.

FIG. 12 is a block diagram illustrating an alternative ConvergedEnhanced network embodiment in accordance with the invention.

DETAILED DESCRIPTION

The invention will now be described more fully hereinafter withreference to the accompanying drawings, in which preferred embodimentsof the invention are shown. Like numbers refer to like elementsthroughout, and like numbers with letter suffixes are used to identifysimilar parts in a single embodiment.

With reference now to FIG. 1, a reliability system 10 for a ConvergedEnhanced Ethernet network 12 is initially described. In an embodiment,the system 10 includes a plurality of end points 14 a-14 n eachcomprising a layer 4 transport layer 16 a-16 n, where each end point isconnected to a data center bridging (DCB) layer 2 network 18. The system10 also includes an adaptor 20 between the layer 4 transport layer 16a-16 n and the DCB layer 2 network 18 to translate at least one of flowand congestion control feedback signals, provided by at least one of theDCB network and the transport layer, to consolidated feedback signalsfor controlling transmission by the transport layer.

In one embodiment, the DCB layer 2 network 18 generates flow controlsignals according to a flow control protocol supporting multiplepriorities, such as Priority Flow Control (PFC) and/or the like. Inanother embodiment, the DCB layer 2 network 18 generates congestioncontrol feedback signals according to a quantized congestionnotification (QCN) protocol.

In one embodiment, the end point 14 a-14 n is connected to the DCB layer2 network 18 through an end station 22, wherein the end stationimplements a quantized congestion notification (QCN) reaction pointimposing rate limits based on a QCN protocol to limit network congestionin the DCB layer 2 network in response to receiving congestion controlsignals. In another embodiment, the network traffic generated by thetransport layer 16 a-16 n is carried on layer 2 18 with lossy operation,either by configuring the end station 22 to steer the traffic to a lossypriority of a priority flow control (PFC) protocol, or by not using anyPFC protocol.

In one embodiment, the network traffic generated by the transport layer16 a-16 n is carried on layer 2 18 with lossless operation, byconfiguring the end station to steer the traffic to a lossless priorityof a priority flow control (PFC) protocol and by letting the end station22 react to layer 2 flow control messages generated by the adjacentswitch 24. In another embodiment, the network traffic generated by thetransport layer 16 a-16 n is carried on layer 2 18 with lossy operation,either by configuring the end station 22 to steer the traffic to a lossypriority of a priority flow control (PFC) protocol, or by not using anyPFC protocol.

In one embodiment, the network traffic generated by the transport layer16 a-16 n is carried on layer 2 18 with lossless operation, byconfiguring the end station 22 to steer the traffic to a losslesspriority of a priority flow control (PFC) protocol and by letting theend station react to layer 2 flow control messages generated by anadjacent switch 24. In another embodiment, the adaptor 20 preprocess theflow and congestion control feedback signals into consolidated feedbacksignals, with the preprocessing including at least one of delaying,aggregating, filtering, replicating, enhancing and decimating theprimary feedback signals.

In one embodiment, the layer 4 transport layer 16 a-16 n is aTransmission Control Protocol (TCP) layer. In another embodiment, theadaptor 20 provides a reduced-rate consolidated feedback signalindicating congestion severity induced by a TCP flow, and in which theadaptor comprises a TCP congestion module for controlling TCP flowtransmissions in response to the consolidated feedback signal.

The consolidated feedback signal may comprise at least one of a TCP flowrate limit, a TCP flow buffer occupancy metric, and a TCP flow ratelimit for processing TCP ACKs and for controlling associated TCPtransmissions. The congestion module adjusts a TCP flow congestionwindow and transmission schedule in response to the consolidatedfeedback signal.

Another aspect of the invention is a reliability method for a ConvergedEnhanced Ethernet network, which is now described with reference toflowchart 32 of FIG. 2. The method begins at Block 34 and may includeproviding a plurality of end points each comprising a layer 4 transportlayer, where each end point is connected to a data center bridging (DCB)layer 2 network at Block 36. The method may also include positioning anadaptor between the layer 4 transport layer and the DCB layer 2 networkto translate at least one of flow and congestion control feedbacksignals, provided by at least one of the DCB network and the transportlayer, to consolidated feedback signals for controlling transmission bythe transport layer at Block 38. The method ends at Block 40.

In another method embodiment, which is now described with reference toflowchart 42 of FIG. 3, the method begins at Block 44. The method mayinclude the steps of FIG. 2 at Blocks 36 and 38. The method may furtherinclude generating flow control signals at the DCB layer 2 networkaccording to a flow control protocol supporting multiple priorities,such as Priority Flow Control (PFC) at Block 46. The method ends atBlock 48.

In another method embodiment, which is now described with reference toflowchart 50 of FIG. 4, the method begins at Block 52. The method mayinclude the steps of FIG. 2 at Blocks 36 and 38. The method mayadditionally include generating congestion control feedback signals atthe DCB layer 2 network according to a quantized congestion notification(QCN) protocol at Block 54. The method ends at Block 56.

In another method embodiment, which is now described with reference toflowchart 58 of FIG. 5, the method begins at Block 60. The method mayinclude the steps of FIG. 4 at Blocks 36, 38, and 54. The method mayalso include connecting the end point to the DCB layer 2 network throughan end station, where the end station implements a quantized congestionnotification (QCN) reaction point imposing rate limits based on a QCNprotocol to limit network congestion in the DCB layer 2 network inresponse to receiving congestion control signals at Block 62. The methodends at Block 64.

In another method embodiment, which is now described with reference toflowchart 66 of FIG. 6, the method begins at Block 68. The method mayinclude the steps of FIG. 4 at Blocks 36, 38, and 54. The method mayfurther include carrying network traffic generated by the transportlayer on layer 2 with lossy operation, either by configuring the endstation to steer the traffic to a lossy priority of a priority flowcontrol (PFC) protocol, or by not using any PFC protocol at Block 70.The method ends at Block 72.

In another method embodiment, which is now described with reference toflowchart 74 of FIG. 7, the method begins at Block 76. The method mayinclude the steps of FIG. 4 at Blocks 36, 38, and 54. The method mayadditionally include carrying the network traffic generated by thetransport layer on layer 2 with lossless operation, by configuring theend station to steer the traffic to a lossless priority of a priorityflow control (PFC) protocol and by letting the end station react tolayer 2 flow control messages generated by an adjacent switch at Block78. The method ends at Block 80.

In another method embodiment, which is now described with reference toflowchart 82 of FIG. 8, the method begins at Block 84. The method mayinclude the steps of FIG. 5 at Blocks 36, 38, 54, and 62. The method mayalso include processing TCP ACKs and ECNs and controlling associated TCPtransmissions where the consolidated feedback signal comprises at leastone of a TCP flow rate limit, a TCP flow buffer occupancy metric, and aTCP flow rate limit at Block 86. The method ends at Block 88.

In another method embodiment, which is now described with reference toflowchart 90 of FIG. 9, the method begins at Block 92. The method mayinclude the steps of FIG. 5 at Blocks 36, 38, 54, and 62. The method mayfurther include adjusting a TCP flow congestion window and transmissionschedule in response to the consolidated feedback signal via thecongestion module at Block 94. The method ends at Block 96.

Another aspect of the invention is a computer readable program codescoupled to tangible media to address reliability in a converged Ethernetnetwork 12. The computer readable program codes may be configured tocause the program to provide a plurality of end points 14 a-14 n eachcomprising a layer 4 transport layer 16 a-16 n respectively, where eachend point is connected to a data center bridging (DCB) layer 2 network18. The computer readable program codes may also position an adaptor 20between the layer 4 transport layer 16 a-16 n and the DCB layer 2network 18 to translate at least one of flow and congestion controlfeedback signals, provided by at least one of the DCB network and thetransport layer, to consolidated feedback signals for controllingtransmission by the transport layer.

In view of the foregoing, the system 10 provides reliability in aConverged Enhanced Ethernet network. For example, current saturationConverged Enhanced Ethernet (CEE) data center networks (DCN) suffer fromtree congestion in the CEE/DCN. CEE datacenters allow high link speedsand short delays while introducing lossless operation (and losslesstraffic classes) by the means of link layer flow control (LL-FC, aka PFCin CEE) beyond the traditional lossy operation (lossy traffic classes).However, in contrast to the traditional Ethernet and Internet, thelossless operation of CEE introduces new challenges, such as deadlocksand saturation tree congestion. Namely, a single hotspot saturation treecongestion can cause a total DCN collapse within a few 10s-100s of us.

FIG. 10 illustrates the problem (hotspot congestion box). If asufficient fraction of all the inputs' traffic targets one of theoutputs (in the figure, the output labeled 128), that output link cansaturate: it becomes a hotspot (HS) that causes the queues in the switchfeeding that link to fill up. If the traffic pattern persists, then, nomatter what techniques are used to reassign buffer space, it is allultimately exhausted. This forces that switch's LL-FC to quicklythrottle back all the inputs feeding that switch. That in turn causesthe previous stage to fill its buffer space. In a domino effect, thecongestion eventually backs up all the way to the network inputs. Thishas been called tree saturation or, in other contexts, high-order Headof Line (HOL) blocking congestion spreading.

Ultimately, the traffic causing the hotspot will root one or moresaturation trees partly caused by the inherent traffic distribution andpartly by flow interference or high-order HOL blocking. Once the tree ofsaturated switches is fully formed, every packet must cross at least onesaturated switch. As the time to exit a queue grows exponentially thefurther a switch is from the hot destination, a majority of the delay isincurred even if only a single switch must be crossed. Hence, thenetwork as a whole suffers a catastrophic loss of throughput: Itsaggregate throughput is gated by the throughput of the single hotoutput.

Saturation spreads very quickly via LL-FC; according to gathered data,the tree is filled in less than 10 traversal times of the network, fartoo quickly for software to react in time to the problem. Naturally, theproblem also dissipates slowly because all the queues involved must beemptied. Hence, a hardware solution is required that reacts quicklyenough to keep the tree from growing large. Clearly the network topologyis irrelevant to this effect; saturation trees can be induced in any DCNtopology.

Thus, lossless LL-FC offers substantial performance benefits, albeit ithas the drawback, besides its complexity, of facilitating saturationtree congestion. Unless an efficient CM protocol is designed andimplemented to control the fabric operation just below the saturationregion and recover from the occasional crossovers, lossless ICTNs suchas CEE-based DCNs will be increasingly exposed to saturation trees andcongestion collapse. However, while the problem is long outstandingdefinitive solutions are not yet practically available. The firstattempts in the CEE context were done in IEEE 802.1Qau, by using the QCNmechanism against simple (single bottleneck), yet persistent, hotspotcongestion.

Why not rely on a widely deployed solution such as transmission controlprotocol (TCP)? The answer is that DCNs and their congestion phenomenaare sufficiently different from the Ethernet (aka Best Effort) andInternet Protocol (IP) networks to invalidate the direct transfer of TCP(even if ECN is added)—that is, without major adaptations—to the DCNenvironment. The main three reasons are: Losslessness: TCP has beendesigned to operate based on loss; packet drops are the basic feedbackmechanism which triggers the source reaction. Packet loss, however,contradicts CEE's principles.

Next, recovery is very/too slow whenever the TCP window is smaller than6 packets. In smaller ICTNs with large MTUs the TCP window size ismostly <6 packets. Conversely, if the recovery is too aggressive,performance may decrease 10-fold. This has been recently validated bythe TCP Incast papers.

Double feedback loop: Unlike TCP in IP networks, FCC mechanisms in DCNsare based on a dual closed-loop control system: (i) LL-FC (PFC) and (ii)end-to-end CM (either QCN, or TCP, or both). The former is the smallerand faster loop taking care of LL correctness and, sometimes,performance like e.g. advanced scheduling [ETS]. CM involves a largerand slower loop with much longer time constants than the LL RTT; acomplete CM solution may include congestion avoidance/prevention andcontrol (after it happens). Since CM is inherently slower than itsunderlying LL-FC loops, it needs an aggregated view of the ICTNstatus—whereas the LL-FC relies only on local status. Thus CM shouldcompensate the inertia of its larger loop by (a) acquiring global view.Feedback (QCN CNM, TCP ECNs, Vegas' delays etc.) about trafficconditions and (b) elaborating a more complex source reaction thatconsiders the outdated global view and ideally, tries to predict thetraffic based on the trends acquired so far. Problem is that TCP doesnot assume the existence of a fast and lossless LL-FC layer; nor doesTCP coexist well with other flow control schemes (QCN), as proven by TCPover ATM/ABR.

Shallow buffers: The alternative would be to over-design the switchbuffers beyond the size mandated for lossless ICTNs. This, however, isnot practically possible (see FIG. 11), but also aggravates thepost-congestion phase by slowing its recovery. Whereas TCP (and ABR)were extensively studied and improved for BE networks, we still lackconclusive evidence of their applicability and sufficiency in ICTNs.Furthermore, recent research invalidates TCP's use for certain types ofmiddleware, as well as the TCP Incast.

TCP was designed in early 80s to curb single bottleneck congestion inlossy BE networks with e2e lags of 100s of ms and 10s of MB switchbuffers. By contrast, a CEE-based DCN is lossless (hencemulti-bottleneck saturation tree congestion), fast (lags of 0.5-50 us)and shallow (10-100s KB) buffers.

In response, system 10 uses the following changes/enhancements to TCP,resulting in “DC-TCP”: 1) Employ a software and/or hardware version ofTCP, such as (CU)BIC, Reno, Vegas, Compound etc. in the end nodes.

2) Disable QCN's controller, if present. Future CEE DCN will implementnative L2 CM, i.e. QCN (see 802.1Qau in [42]). Retain the QCN congestiondetection, while disabling the QCN rate limiter in the source.

3) Congestion signaling and TCP rate limiter: Replace or complement thetraditional TCP rate limiter based on duplicate ACKs with a hybrid ratelimiter based on backward congestion notifications (BCNs) and QCNcongestion notification messages (CNMs). Feed a digested form of CNMsassociated with the TCP source into TCP for window control based on L2feedback.

4) Detect and compensate for saturation tree. Re-tune the TCP constants(e.g. RTO) based on the DCN topology and size. Potentially adapt tochanging network size and delay in real time (optional, via delayprobing or Feedback Request protocol).

One challenge will be that congestion may occur in an external Ethernetnetwork that may be lossy, in which case congestion may result in packetloss and ensuing duplicate ACKs from the TCP receiver. This is aboutinteroperability of DC-TCP with TCP in the external network. Hence theneed for a hybrid rate limiter that understands BCNs, digested CNMs, aswell as duplicate ACKs.

In case of a DC-TCP sender and a TCP receiver in a lossy network, theTCP receiver will report congestion/loss in the lossy network viaduplicate ACKs. In case of a TCP sender in a lossy network andcongestion occurring in a lossless network leading to the DC-TCPreceiver, the CNMs sent towards the source must be appropriatelytranslated at the boundary between the lossless and the lossy networks.One possibility is to convert CNMs to TCP window scalings in theboundary switch, as CNMs will not be understood by the lossy network.

While dozens of TCP flavors have been published, generally they dealwith fast WANs (same rate as DCNs, but long delays) or wirelessapplications. Lossless apps of TCP, dealing with saturation trees(multiple correlated bottlenecks) and also working with shallow buffersare not known thus far. Furthermore, TCP has not yet been combined withL2 congestion detection mechanisms such as QCN, which provides amulti-bit (ECN/BCN is commonly binary) quantitative feedback. Toeffectively curb DCN congestion, optionally we additionally (may) applythe compensation scheme described above. FIG. 12 illustrates oneembodiment of system 10.

System 10 adapts TCP to a lossless DCN, by combining a re-tuned TCPflavor (CUBIC, Compound and New Reno are favored, others may apply) withL2 QCN signaling. System 10 copes with saturation trees issues, uslatency, and shallow buffers.

System 10 also compensates and adapts to rapidly changing DCN loads.System 10 provided full TCP socket compatibility, and therefore legacyapplication support.

In a CEE-based data center network 12, a method for preventing thespread of packet congestion while simultaneously preventing packet lossin the network having at least one source channel adapter, at least onedestination channel adapter, and multiple fiber channel over Ethernet(FCoE) enabled switches 24 is enabled by system 10. The system 10detects congestion occurring within the data center network. The system10 measures the extent of the congestion and generates a feedback signal(value) at the Layer 2 level, notifying the source channel adapter anddestination channel adapter that congestion is occurring. The system 10also compensates for that congestion by changing the packet injectionrate (within a sliding window) by an amount proportional to themagnitude of the feedback signal and dynamically readjusts the feedbacksignal (value) based on the extent of congestion.

It should be noted that in some alternative implementations, thefunctions noted in a flowchart block may occur out of the order noted inthe figures. For instance, two blocks shown in succession may, in fact,be executed substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionality involvedbecause the flow diagrams depicted herein are just examples. There maybe many variations to these diagrams or the steps (or operations)described therein without departing from the spirit of the invention.For example, the steps may be performed concurrently and/or in adifferent order, or steps may be added, deleted, and/or modified. All ofthese variations are considered a part of the claimed invention.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

While the preferred embodiment to the invention has been described, itwill be understood that those skilled in the art, both now and in thefuture, may make various improvements and enhancements which fall withinthe scope of the claims which follow. These claims should be construedto maintain the proper protection for the invention first described.

1. A system comprising: a plurality of end points each comprising alayer 4 transport layer, where each end point is connected to a datacenter bridging (DCB) layer 2 network; and an adaptor between the layer4 transport layer and the DCB layer 2 network to translate at least oneof flow and congestion control feedback signals provided by at least oneof the DCB network and the transport layer, to consolidated feedbacksignals for controlling transmission by the transport layer.
 2. Thesystem of claim 1 wherein the DCB layer 2 network generates flow controlsignals according to a flow control protocol supporting multiplepriorities.
 3. The system of claim 1 wherein the DCB layer 2 networkgenerates congestion control feedback signals according to a quantizedcongestion notification (QCN) protocol.
 4. The system of claim 3 whereinthe end point is connected to the DCB layer 2 network through an endstation, where the end station implements a quantized congestionnotification (QCN) reaction point imposing rate limits based on a QCNprotocol to limit network congestion in the DCB layer 2 network inresponse to receiving congestion control signals.
 5. The system of claim3 wherein the network traffic generated by the transport layer iscarried on layer 2 with lossy operation, either by configuring the endstation to steer the traffic to a lossy priority of a priority flowcontrol (PFC) protocol, or by not using any PFC protocol.
 6. The systemof claim 3 wherein the network traffic generated by the transport layeris carried on layer 2 with lossless operation, by configuring the endstation to steer the traffic to a lossless priority of a priority flowcontrol (PFC) protocol and by letting the end station react to layer 2flow control messages generated by the adjacent switch.
 7. The system ofclaim 4 wherein the network traffic generated by the transport layer iscarried on layer 2 with lossy operation, either by configuring the endstation to steer the traffic to a lossy priority of a priority flowcontrol (PFC) protocol, or by not using any PFC protocol.
 8. The systemof claim 4 wherein the network traffic generated by the transport layeris carried on layer 2 with lossless operation, by configuring the endstation to steer the traffic to a lossless priority of a priority flowcontrol (PFC) protocol and by letting the end station react to layer 2flow control messages generated by an adjacent switch.
 9. The system ofclaim 1 wherein the adaptor preprocesses the flow and congestion controlfeedback signals into consolidated feedback signals, with thepreprocessing including at least one of delaying, aggregating,filtering, replicating, enhancing and decimating the primary feedbacksignals. 10-17. (canceled)
 18. A computer program product embodied in atangible media comprising: computer readable program codes coupled tothe tangible media to improve reliability of a converged Ethernetnetwork, the computer readable program codes configured to cause theprogram to: provide a plurality of end points each comprising a layer 4transport layer, where each end point is connected to a data centerbridging (DCB) layer 2 network; and position an adaptor between thelayer 4 transport layer and the DCB layer 2 network to translate atleast one of flow and congestion control feedback signals, provided byat least one of the DCB network and the transport layer, to consolidatedfeedback signals for controlling transmission by the transport layer.19. The computer program product of claim 18 further comprising programcode configured to: generate flow control signals at the DCB layer 2network according to a flow control protocol supporting multiplepriorities, such as Priority Flow Control (PFC).
 20. The computerprogram product of claim 18 further comprising program code configuredto: generate congestion control feedback signals at the DCB layer 2network according to a quantized congestion notification (QCN) protocol21. The computer program product of claim 20 further comprising programcode configured to: connect the end point to the DCB layer 2 networkthrough an end station, where the end station implements a quantizedcongestion notification (QCN) reaction point imposing rate limits basedon a QCN protocol to limit network congestion in the DCB layer 2 networkin response to receiving congestion control signals.
 22. The computerprogram product of claim 20 further comprising program code configuredto: carry network traffic generated by the transport layer on layer 2with lossy operation, either by configuring the end station to steer thetraffic to a lossy priority of a priority flow control (PFC) protocol,or by not using any PFC protocol.
 23. The computer program product ofclaim 20 further comprising program code configured to: carrying thenetwork traffic generated by the transport layer on layer 2 withlossless operation, by configuring the end station to steer the trafficto a lossless priority of a priority flow control (PFC) protocol and byletting the end station react to layer 2 flow control messages generatedby an adjacent switch.
 24. The computer program product of claim 21further comprising program code configured to: processing TCP ACKs andcontrolling associated TCP transmissions where the consolidated feedbacksignal comprises at least one of a TCP flow rate limit, a TCP flowbuffer occupancy metric, and a TCP flow rate limit.
 25. The computerprogram product of claim 21 further comprising program code configuredto: adjusting a TCP flow congestion window and transmission schedule inresponse to the consolidated feedback signal via the congestion module.